Defining Event-Based Subprocesses
Create an interrupting or non-interrupting event-based subprocess.
A subprocess which does not have any inflowing or outflowing sequence flows is inserted in the BPMN process.
The respective events can only be used in event-based subprocesses as start events for the following event definitions:
- Hazard
- Escalation
- Compensation
An event with one of these event definitions can only be defined as a start event for event-based subprocesses.
The following event definitions cannot be used for start events in event-based subprocesses:
- Failed completion
- Terminate
The decision whether an event-based subprocess is interrupting or non-interrupting is made at the respective start event.
- Right click on the subprocess and select the is triggered by an event subprocess type from the mini toolbar:
Or activate the corresponding property in the Properties window.The subprocess is shown as an event-based subprocess.
- Insert a start event with an appropriate event definition or convert an existing event into a start event.
The event is always initially shown as an interrupting event.
- To mark the start event as non-interrupting, deactivate the is interrupting check box in the Properties window.
The event is shown as a non-interrupting start event.
An empty event (with no event definition) is always inserted in an event-based subprocess as an end event. Only when the event has been linked to a suitable event definition can it be defined as a start event.
Related Topics